Method and apparatus for processing a communication request from a roaming voice over ip terminal

ABSTRACT

An apparatus and method are disclosed for processing a communication request from a roaming VoIP terminal. An apparatus that incorporates teachings of the present disclosure may include, for example, a network proxy having a controller that manages a communications interface in a communication system. The controller can be programmed to receive from a Voice over IP (VoIP) terminal a request to communicate with a destination point, wherein the request comprises an identification (ID) of the destination point, an ID of the VoIP terminal, and a media access control (MAC) address of a gateway providing the VoIP terminal communication access to the network proxy, and determine from the MAC address of the gateway and the ID of the VoIP terminal whether the VoIP terminal is roaming outside of a home network. Additional embodiments are disclosed.

RELATED APPLICATION

U.S. Patent Application, filed Jun. 13, 2006, by Gorti et al., entitled“Method and Apparatus for Processing Session Initiation ProtocolMessages Associated with a Voice Over IP Terminal,” incorporated hereinby reference in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to Voice over IP (VoIP)communications, and more specifically to a method and apparatus forprocessing a communication request from a roaming VoIP terminal.

BACKGROUND

Multimode VoIP terminals can roam on a number of wired or wirelessaccess technologies by way of a common gateway such as a residentialgateway. Because of the nomadic nature of multimode VoIP terminals, itcan be difficult to know when said terminals are roaming outside of ahome network (e.g., a residence or commercial enterprise) since what isgenerally known about the terminal is its IP address which is not fixedto a single location. It is similarly a challenge to locate the VoIPterminal once it has roamed outside of its home network.

These complications can make call processing problematic for serviceproviders especially in situations where the caller is attempting tocommunicate with an emergency response center such as a public serviceaccess point (PSAP) for 911 services which requires knowledge of theterminal's location to comply with Federal Communications Commission(FCC) regulations.

A need therefore arises for a method and apparatus for processing acommunication request from a roaming VoIP terminal.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an exemplary embodiment of multimode VoIP terminalscommunicating by way of wired and wireless access points (WAPs) withother communication devices and/or a network proxy which collectivelyoperate in a communication system;

FIG. 2 depicts exemplary embodiments of the multimode VoIP terminal;

FIG. 3 depicts an exemplary method operating in portions of thecommunication system; and

FIG. 4 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system within which a set of instructions, whenexecuted, may cause the machine to perform any one or more of themethodologies disclosed herein.

DETAILED DESCRIPTION OF THE DRAWINGS

Embodiments in accordance with the present disclosure provide a methodand apparatus for processing a communication request from a roaming VoIPterminal.

In a first embodiment of the present disclosure, a network proxy canhave a controller that manages a communications interface in acommunication system. The controller can be programmed to receive from aVoice over IP (VoIP) terminal a request to communicate with adestination point, wherein the request comprises an identification (ID)of the destination point, an ID of the VoIP terminal, and a media accesscontrol (MAC) address of a gateway providing the VoIP terminalcommunication access to the network proxy, and determine from the MACaddress of the gateway and the ID of the VoIP terminal whether the VoIPterminal is roaming outside of a home network.

In a second embodiment of the present disclosure, a computer-readablestorage medium in a VoIP terminal can have computer instructions forrequesting from a gateway its media access control (MAC) address, andtransmitting to a network proxy a request to communicate with adestination point, wherein the request comprises the MAC address of thegateway.

In a third embodiment of the present disclosure, a gateway can have acontroller programmed to transmit the gateway's MAC address to a VoIPterminal, and transmitting to a network proxy a request received fromthe VoIP terminal to communicate with a destination point, wherein therequest comprises the MAC address of the gateway.

In a fourth embodiment of the present disclosure, a gateway can have acontroller programmed to detect a request from a VoIP terminal tocommunicate with a emergency response center, and transmitting to anetwork proxy the request with a MAC address of the gateway for enablingcommunications between the VoIP terminal and the emergency responsecenter.

FIG. 1 depicts an exemplary embodiment of multimode VoIP terminals 116communicating by way of wired and wireless access points (WAPs) withother communication devices and/or a network proxy 102 whichcollectively operate in a communication system 100. The communicationsystem 100 comprises an IP (Internet Protocol) network 101 coupled tothe network proxy 102, a cellular network 103 and network elementslocated in a building 105 representing an enterprise or residence. TheIP network 101 utilizes technology for transporting Internet traffic.

In an enterprise setting, the building 105 can include a gateway (GW)114 that provides voice and/or video connectivity services between VoIPterminals 116 or other forms of communication devices of enterprisepersonnel. In a residential setting, the building 105 can include a GW114 represented by, for example, a residential gateway coupled to acentral office 113 utilizing conventional telephonic switching forprocessing calls with third parties.

The network proxy 102 can be used to control operations of a mediagateway 109, the central office 113 and the GW 114. Communicationsbetween the network proxy 102, VoIP terminals 116 and other networkelements of the communication system 100 can conform to any number ofsignaling protocols such as a session initiation protocol (SIP), or avideo communications protocol such as H.323 which combines video andvoice over a packet-switched network.

The network proxy 102 can comprise a communications interface 104 thatutilizes common technology for communicating over an IP interface withthe IP network 101, the media gateway 109, the cellular network 103,and/or the GW 114. By way of the communications interface 104, thenetwork proxy 102 can direct by common means any of the foregoingnetwork elements to establish packet switched data, voice, and/or videoconnections between VoIP terminals 116 distributed throughout thecommunication system 100. The network proxy 102 further comprises amemory 106 (such as a high capacity storage medium) embodied in thisillustration as a database, and a controller 108 that makes use ofcomputing technology such as a desktop computer, or scalable server forcontrolling operations of the network proxy 102. The network proxy 102can operate as an IP Multimedia Subsystem (IMS) conforming in part toprotocols defined by standards bodies such as 3GPP (Third GenerationPartnership Protocol).

Under the control of the network proxy 102, the media gateway 109 canlink packet-switched and circuit-switched technologies such as thecellular network 103 (or central office 113) and the IP network 101,respectively. The media gateway 109 can conform to a media gatewaycontrol protocol (MGCP) also known as H.248 defined by work groups inthe Internet Engineering Task Force (IETF). This protocol can handlesignaling and session management needed during a multimedia conference.The protocol defines a means of communication which converts data fromthe format required for a circuit-switched network to that required fora packet-switched network. MGCP can therefore be used to set up,maintain, and terminate calls between multiple disparate networkelements of the communication system 100. The media gateway 109 cantherefore support hybrid communication environments for VoIP terminals116.

The cellular network 103 can support voice and data services over anumber of access technologies such as GSM-GPRS, EDGE, CDMA-1X, UMTS,WiMAX, software defined radio (SDR), and other known and futuretechnologies. The cellular network 103 can be coupled to base stations107 under a frequency-reuse plan for communicating over-the-air withroaming VoIP terminals 116.

FIG. 2 depicts exemplary embodiments of the multimode VoIP terminal 116.In one embodiment, the VoIP terminal 116 can be embodied in an immobiledevice (e.g., a wireline phone). In another embodiment, the VoIPterminal 116 can include short range communications technology (e.g., acordless phone, Bluetooth or WiFi) to support mobility within a smallarea such as the end user's residence or office.

Additionally, the VoIP terminal 116 can utilize a wireless transceiver202 that supports long-range wireless communications such as supportedby the cellular network 103, or for roaming between WiFi and/or WiMAXaccess networks. In this embodiment, the wireless transceiver 202 ofVoIP terminal 116 can utilize technology for exchanging voice and datamessages with the base stations 107 (or WiFi and WiMAX access points),which in turn can relay said messages to targeted end user terminals116.

A multimode VoIP terminal 116 can support a combination of some or allof the aforementioned wireless and wireline access technologies (e.g.,POTS, WiFi, WiMAX, Bluetooth™, cordless, and cellular).

Each of the embodiments of the VoIP terminal 116 can further include amemory 204, an audio system 206, a location determination device 205, aradio frequency identification (RFID) device 207, and a controller 208.The memory 204 can comprise storage devices such as RAM, SRAM, DRAM,and/or Flash memories. The memory 204 can be an integral part of thecontroller 208. The audio system 206 can comprise a low volume speakerfor listening to messages near the end user's ear and an associatedmicrophone for exchanging messages with calling parties. The audiosystem 206 can further utilize a loud speaker for listening toannouncements at a distance substantially away from the end user's ear,and as a speakerphone feature.

The location determination device 205 can represent a global positioningsystem (GPS) receiver for determining a location fix of the VoIPterminal 116. The RFID device 207 can represent a passive or active RFIDfor short-range communications. The RFID device 207 can be used forretrieving information such as the media access control (MAC) address ofthe GW 114 and/or its location. In this embodiment the GW 114 would alsoinclude a similar RFID device (although not shown in FIG. 1).

The controller 208 can manage the foregoing components with computingtechnology such as a microprocessor and/or digital signal processor. TheVoIP terminals 116 can further include a display 210 for conveyingimages to the end user, a keypad 212 for manipulating operations of theVoIP terminal 116, and a portable power supply 213. The audio system206, display 210, and the keypad 212 can singly or in combinationrepresent a user interface (UI) for interfacing with the end user.

FIG. 3 depicts an exemplary method 300 operating in portions of thecommunication system 100. Method 300 has many variants as depicted bythe dashed lines. It would be apparent to an artisan with ordinary skillin the art that other embodiments not depicted in FIG. 3 are possiblewithout departing from the scope of the claims described below.

With this in mind, in one embodiment, method 300 begins with step 302 inwhich a VoIP terminal 116 can be programmed to receive a request from anend user to establish service with the network proxy 102 orcommunications with a destination point. The request can thereforerepresent a registration of the VoIP terminal 116 with the network proxy102, or a mobile or network origination call invoked by the end user bydialing a phone number. The destination point can be another VoIPterminal 116, an emergency response center such as a public serviceaccess point (PSAP—911), and/or a POTS or circuit-switched communicationterminal. For illustration purposes only, the destination point will beassumed to be a PSAP.

In step 304, the VoIP terminal 116 queries the GW 114 for its MACaddress utilizing an address resolution protocol (ARP) or any othercommon technique for retrieving the GW's MAC address. In the same step,the VoIP terminal 116 forwards the request for service registration, orcommunications with the destination point to the network proxy 102. Inthe case of registration, the request can include an ID of the VoIPterminal 116 (such as, for example, its MAC address), and the MACaddress of the GW 114. In the case of a communication request, therequest can further include an identification (ID) of the PSAP (e.g.,911 or other emergency code). In step 306, the network proxy 102receives and processes the request for service or to communicate withthe PSAP, and in step 308 determines whether the VoIP terminal 116 hasroamed outside of its home network (e.g., the end user's residence oroffice).

The network proxy 102 can determine that the VoIP terminal 116 isroaming by comparing the MAC address of the GW 114 associated with theVoIP terminal's 116 home network and the MAC address received with therequest. If the MAC address received does not match with the MAC addressof the GW's 114 home network, the network proxy 102 can conclude in step308 that the VoIP terminal 116 is roaming. Determining whether or notthe VoIP terminal 116 is roaming can be managed by way of a commondatabase operating in the network proxy 102. The MAC address of the GW114 located in the VoIP terminal's 116 home network, and the GW'slocation can be stored in the database, and can be indexed by way of theMAC address (or other form of ID) of the VoIP terminal.

If the network proxy 102 detects in step 308 that the VoIP terminal 116is in its home network, the network proxy 102 can establish service andproceed to step 312 whereby it establishes communications between theVoIP terminal and the PSAP and supplies to the PSAP the VoIP terminal'slocation derived from the GW's home network stored in the networkproxy's 102 database. Since gateways are generally immobile devices, thelocation given can be relied on as the location of the VoIP terminal116. If instead the network proxy 102 detects in step 308 that the VoIPterminal 116 is roaming by way of detecting a mismatch between the MACaddress received and that of its home network, the network proxy 102 canproceed to one among steps 310, 320 and 328.

In step 310, the network proxy 102 can determine the location of theVoIP terminal 116 by way of associating the MAC address of the GW 114received and a corresponding location stored in the database of thenetwork proxy 102. In this embodiment, the network proxy 102 can beprogrammed to store the locations of each of the GWs 114 which the VoIPterminal 116 might roam to. This may be possible by tracking the GWs 114of a service provider and by sharing location information of GWs 114outside the reach of the service provider through brokering deals, or byFCC mandate to share GW location information across all serviceproviders. Once the GW 114 in question is located, the network proxy 102can establish service, and proceed to step 312 and enable communicationswith the PSAP with the location of the VoIP terminal supplied to thePSAP as described earlier.

In another embodiment, the network proxy 102 can be programmed in step320 to transmit to the VoIP terminal 116 a location request. In step322, the VoIP terminal 116 can direct the location request to its enduser by way of the UI. In step 324, the network proxy 102 can exchangemessages with the end user by way of the UI of the VoIP terminal 116.The messages exchanged can be text, voice, Dual Tone Multi-Frequency(DTMF) signals, or combinations thereof processed by, for example, aninteractive voice response system (IVR) integrated with the networkproxy 102 or managed thereby From the interactions with the end user(e.g., end user dictates his/her location, or enters location by way oftext through the UI), the network proxy 102 in step 326 identifies alocation of the VoIP terminal 116 and proceeds to step 312 to enablecommunications between the VoIP terminal 116 and the PSAP with locationinformation.

In yet another embodiment, the network proxy 102 can be programmed instep 328 to reject the service and communication request received fromthe VoIP terminal 116 while it is roaming. In this embodiment, the VoIPterminal 116 can only make certain calls such as emergency responsecenter calls from its home network. In a less restrictive embodiment,step 328 can be combined with steps 320-326 to overcome the rejection byway of proactive feedback from the end user of the VoIP terminal 116.

Referring back to step 302, the VoIP terminal 116 can be programmed inanother embodiment to submit in step 314 the request to communicate withthe PSAP to the network proxy 102 without querying the GW 114 for itsMAC address. In step 316 the GW 114 can be programmed to detect therequest from the VoIP terminal 116 and proactively insert or append itsMAC address to the request. This embodiment replaces the need for theVoIP terminal 116 to query the GW 114 for its MAC address. Steps 306-328can be applied to this embodiment as previously described.

In yet another embodiment, the VoIP terminal 116 can be programmed instep 302 to proceed to step 318 where it detects and extracts locationinformation from an RFID device located at the GW 114, or from thelocation determination device 205 of the VoIP terminal 116. Once thelocation information is retrieved, the VoIP terminal 116 transmits therequest and location to the network proxy 102. Since locationinformation is given with the request, the network proxy 102 can beprogrammed to proceed from step 306 to step 312 thereby enablingcommunications between the VoIP terminal 116 and the PSAP. It istherefore not necessary to determine in step 308 whether the VoIPterminal 116 is roaming since its location is known.

It would be apparent to an artisan with ordinary skill in the art fromthe aforementioned exemplary embodiments that there can be numerousother embodiments applied to the present disclosure. Accordingly, saidartisan would expect that the present embodiments can be modified,reduced, or enhanced without departing from the scope and spirit of theclaims described below. The reader is therefore directed to the claimsbelow for a fuller understanding of the breadth and scope of the presentdisclosure.

FIG. 4 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 400 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethodologies discussed above. In some embodiments, the machine operatesas a standalone device. In some embodiments, the machine may beconnected (e.g., using a network) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient user machine in server-client user network environment, or as apeer machine in a peer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet PC, a laptop computer, a desktopcomputer, a control system, a network router, switch or bridge, or anymachine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a device of the present disclosure includes broadly anyelectronic device that provides voice, video or data communication.Further, while a single machine is illustrated, the term “machine” shallalso be taken to include any collection of machines that individually orjointly execute a set (or multiple sets) of instructions to perform anyone or more of the methodologies discussed herein.

The computer system 400 may include a processor 402 (e.g., a centralprocessing unit (CPU), a graphics processing unit (GPU, or both), a mainmemory 404 and a static memory 406, which communicate with each othervia a bus 408. The computer system 400 may further include a videodisplay unit 410 (e.g., a liquid crystal display (LCD), a flat panel, asolid state display, or a cathode ray tube (CRT)). The computer system400 may include an input device 412 (e.g., a keyboard), a cursor controldevice 414 (e.g., a mouse), a disk drive unit 416, a signal generationdevice 418 (e.g., a speaker or remote control) and a network interfacedevice 420.

The disk drive unit 416 may include a machine-readable medium 422 onwhich is stored one or more sets of instructions (e.g., software 424)embodying any one or more of the methodologies or functions describedherein, including those methods illustrated above. The instructions 424may also reside, completely or at least partially, within the mainmemory 404, the static memory 406, and/or within the processor 402during execution thereof by the computer system 400. The main memory 404and the processor 402 also may constitute machine-readable media.

Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices can likewise be constructed to implement themethods described herein. Applications that may include the apparatusand systems of various embodiments broadly include a variety ofelectronic and computer systems. Some embodiments implement functions intwo or more specific interconnected hardware modules or devices withrelated control and data signals communicated between and through themodules, or as portions of an application-specific integrated circuit.Thus, the example system is applicable to software, firmware, andhardware implementations.

In accordance with various embodiments of the present disclosure, themethods described herein are intended for operation as software programsrunning on a computer processor. Furthermore, software implementationscan include, but not limited to, distributed processing orcomponent/object distributed processing, parallel processing, or virtualmachine processing can also be constructed to implement the methodsdescribed herein.

The present disclosure contemplates a machine readable medium containinginstructions 424, or that which receives and executes instructions 424from a propagated signal so that a device connected to a networkenvironment 426 can send or receive voice, video or data, and tocommunicate over the network 426 using the instructions 424. Theinstructions 424 may further be transmitted or received over a network426 via the network interface device 420.

While the machine-readable medium 422 is shown in an example embodimentto be a single medium, the term “machine-readable medium” should betaken to include a single medium or multiple media (e.g., a centralizedor distributed database, and/or associated caches and servers) thatstore the one or more sets of instructions. The term “machine-readablemedium” shall also be taken to include any medium that is capable ofstoring, encoding or carrying a set of instructions for execution by themachine and that cause the machine to perform any one or more of themethodologies of the present disclosure.

The term “machine-readable medium” shall accordingly be taken toinclude, but not be limited to: solid-state memories such as a memorycard or other package that houses one or more read-only (non-volatile)memories, random access memories, or other re-writable (volatile)memories; magneto-optical or optical medium such as a disk or tape; andcarrier wave signals such as a signal embodying computer instructions ina transmission medium; and/or a digital file attachment to e-mail orother self-contained information archive or set of archives isconsidered a distribution medium equivalent to a tangible storagemedium. Accordingly, the disclosure is considered to include any one ormore of a machine-readable medium or a distribution medium, as listedherein and including art-recognized equivalents and successor media, inwhich the software implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the disclosure is not limited to such standards andprotocols. Each of the standards for Internet and other packet switchednetwork transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) representexamples of the state of the art. Such standards are periodicallysuperseded by faster or more efficient equivalents having essentiallythe same functions. Accordingly, replacement standards and protocolshaving the same functions are considered equivalents.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Otherembodiments may be utilized and derived therefrom, such that structuraland logical substitutions and changes may be made without departing fromthe scope of this disclosure. Figures are also merely representationaland may not be drawn to scale. Certain proportions thereof may beexaggerated, while others may be minimized. Accordingly, thespecification and drawings are to be regarded in an illustrative ratherthan a restrictive sense.

Such embodiments of the inventive subject matter may be referred toherein, individually and/or collectively, by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed. Thus, although specific embodiments havebeen illustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the above description.

The Abstract of the Disclosure is provided to comply with 47 C.F.R.§1.72(b), requiring an abstract that will allow the reader to quicklyascertain the nature of the technical disclosure. It is submitted withthe understanding that it will not be used to interpret or limit thescope or meaning of the claims. In addition, in the foregoing DetailedDescription, it can be seen that various features are grouped togetherin a single embodiment for the purpose of streamlining the disclosure.This method of disclosure is not to be interpreted as reflecting anintention that the claimed embodiments require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive subject matter lies in less than all features of asingle disclosed embodiment. Thus the following claims are herebyincorporated into the Detailed Description, with each claim standing onits own as a separately claimed subject matter.

1. A network proxy, comprising a controller that manages acommunications interface in a communication system, wherein thecontroller is programmed to: receive from a Voice over IP (VoIP)terminal a request to communicate with a destination point, wherein therequest comprises an identification (ID) of the destination point, an IDof the VoIP terminal, and a media access control (MAC) address of agateway providing the VoIP terminal communication access to the networkproxy; and determine from the MAC address of the gateway and the ID ofthe VoIP terminal whether the VoIP terminal is roaming outside of a homenetwork.
 2. The network proxy of claim 1, wherein the ID of the VoIPterminal comprises the VoIP terminal's MAC address.
 3. The network proxyof claim 1, wherein the controller is programmed to reject the requestfor communications in response to a determination that the VoIP terminalis roaming outside of its home network.
 4. The network proxy of claim 1,wherein the destination point comprises an emergency response center,and wherein the controller is programmed to: determine a location of thegateway according to its MAC address in response to a determination thatthe VoIP terminal is roaming outside of its home network; and establishcommunications between the VoIP terminal and the emergency responsecenter and supply the emergency response center the location.
 5. Thenetwork proxy of claim 1, wherein the destination point comprises anemergency response center, and wherein the controller is programmed to:transmit to the VoIP terminal a location request; receive a location ofthe VoIP terminal; and establish communications between the VoIPterminal and the emergency response center and supply the emergencyresponse center the location.
 6. The network proxy of claim 5, whereinthe location request is directed to an end user of the VoIP terminal,and wherein the controller is programmed to exchange messages with theend user by way of the VoIP terminal to determine the location of theend user.
 7. The network proxy of claim 6, wherein the messagescorrespond to at least one among voice and Dual Tone Multi-Frequency(DTMF) signals generated by the end user by way of the VoIP terminal. 8.The network proxy of claim 1, wherein the request is transported in asession initiation protocol (SIP), and wherein the destination pointcomprises a public service access point (PSAP).
 9. The network proxy ofclaim 1, wherein the network proxy comprises an Internet protocolMultimedia Subsystem (IMS), and wherein the gateway comprises aresidential gateway.
 10. The network proxy of claim 1, wherein thecontroller is programmed to establish communications between the VoIPterminal and the destination point and supply the destination point alocation of the VoIP terminal determined from the MAC address of thegateway upon determining that the VoIP terminal is communicating fromthe home network.
 11. A computer-readable storage medium in a VoIPterminal, comprising computer instructions for: requesting from agateway its media access control (MAC) address; and transmitting to anetwork proxy a request to communicate with a destination point, whereinthe request comprises the MAC address of the gateway.
 12. The storagemedium of claim 11, comprising computer instructions for determining theMAC address according to an address resolution protocol (ARP).
 13. Thestorage medium of claim 11, comprising computer instructions forformatting the request according to a session initiation protocol (SIP).14. The storage medium of claim 11, wherein the request furthercomprises the VoIP terminal's MAC address.
 15. The storage medium ofclaim 11, comprising computer instructions for: detecting a radiofrequency identification (RFID) device associated with the gateway;determining a location of the VoIP terminal from location informationreceived from the RFID; and transmitting to the network proxy thelocation of the VoIP terminal for enabling communications between theVoIP terminal and the destination point.
 16. The storage medium of claim11, comprising computer instructions for: receiving from the networkproxy a location information request; presenting the locationinformation request to an end user of the VoIP; receiving a location ofthe VoIP from the end user; and transmitting to the network proxy thelocation of the VoIP terminal for enabling communications between theVoIP terminal and the destination point.
 17. The storage medium of claim11, comprising computer instructions for: determining a location of theVoIP terminal; and transmitting to the network proxy the location of theVoIP terminal for enabling communications between the VoIP terminal andthe destination point.
 18. The storage medium of claim 11, wherein thelocation is determined from a location determination device of the VoIPterminal.
 19. The storage medium of claim 11, wherein the gatewaycomprises a residential gateway.
 20. The storage medium of claim 11,comprising computer instructions for registering at the network proxythe VoIP terminal with the MAC address of the gateway to establishservice.
 21. A gateway, comprising a controller programmed to: transmitthe gateway's MAC address to a VoIP terminal; and transmit to a networkproxy a request received from the VoIP terminal to communicate with adestination point, wherein the request comprises the MAC address of thegateway.
 22. The gateway of claim 21, wherein the controller isprogrammed to transmit to the VoIP terminal a location of the gateway,wherein the request includes the location of the gateway for enablingcommunications with the destination point.
 23. The gateway of claim 21,wherein the gateway comprises a residential gateway.
 24. A gateway,comprising a controller programmed to: detect a request from a VoIPterminal to communicate with a emergency response center; and transmitto a network proxy the request with a MAC address of the gateway forenabling communications between the VoIP terminal and the emergencyresponse center.
 25. The gateway of claim 24, wherein the gatewaycomprises a residential gateway.